Merging Instant Messaging (IM) Chat Sessions

ABSTRACT

The present disclosure provides for merging of instant messaging (IM) chat sessions. In one embodiment, a method for automatically replying to an IM message from a first IM sender when a recipient is engaged in an IM session with a second IM sender is provided. In another embodiment, the disclosure provides a method for forwarding IM messages to a recipient at different IM clients. In still another embodiment, a method for transferring IM messages to a different recipient is provided. In some embodiments, two separate IM chat sessions are merged into a single IM chat session.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/902,097 filed Oct. 11, 2010, which is a continuation of U.S. patentapplication Ser. No. 10/685,562 filed Oct. 14, 2003, now U.S. Pat. No.7,844,662, which claims the benefit of U.S. patent application Ser. No.10/274,405, filed Oct. 18, 2002; U.S. patent application Ser. No.10/274,408, filed Oct. 18, 2002; U.S. patent application Ser. No.10/274,478, filed Oct. 18, 2002; U.S. patent application Ser. No.10/325,290, filed Dec. 19, 2002; U.S. patent application Ser. No.10/364,693, filed Feb. 10, 2003; U.S. patent application Ser. No.10/364,703, filed Feb. 10, 2003; U.S. Provisional Patent ApplicationSer. No. 60/411,336, filed Sep. 17, 2002; U.S. Provisional PatentApplication Ser. No. 60/411,438, filed Sep. 17, 2002; U.S. ProvisionalPatent Application Ser. No. 60/416,916, filed Oct. 8, 2002; U.S.Provisional Patent Application Ser. No. 60/419,613 filed on Oct. 17,2002; U.S. Provisional Patent Application Ser. No. 60/426,145, filedNov. 14, 2002; U.S. Provisional Patent Application Ser. No. 60/426,146,filed Nov. 14, 2002; U.S. Provisional Patent Application Ser. No.60/426,422, filed Nov. 14, 2002; U.S. Provisional Patent ApplicationSer. No. 60/426,432, filed Nov. 14, 2002; and U.S. Provisional PatentApplication Ser. No. 60/426,440, filed Nov. 14, 2002, all of which areincorporated by reference in their entireties.

FIELD OF THE INVENTION

The present disclosure relates generally to digital communications and,more particularly, to instant messaging (IM).

BACKGROUND

The explosive growth of digital communications media has supplementedconventional forms of communication. One example of digitalcommunications is instant messaging (IM). As known to those having skillin the art, the IM environment is defined in RFC 2778 and RFC 2779,which was published by the Internet Engineering Task Force (IETF) inFebruary of 2000. Briefly, the IM environment provides a medium in whichdigital communications occurs on a near real-time basis between a senderand a recipient, thereby permitting a sender to send and receive“instant” messages to and from a recipient.

While the near real-time communication of IM is appealing, IMnonetheless has several drawbacks. For example, unlike face-to-faceconversations, when the recipient steps away from the recipient'sworkstation for a moment, the sender may send messages to the recipientwithout any knowledge that the recipient is no longer at theworkstation. In order to remedy this deficiency, others have manipulatedpresence mechanisms of IM to display presence-status indications (alsoreferred to simply as “status indications”) that are indicative of therecipient's absence. For example, these status indications may includemessages that indicate that the recipient is “away,” “busy,”“unavailable,” etc.

As is known in the art, the status indications may be manually set bythe recipient prior to the recipient's absence from the workstation.Alternatively, the status indications may be programmed to activateafter a predefined time interval when there is no activity at therecipient's workstation and programmed to deactivate when the recipientbegins typing again. Unfortunately, the status indications provide onlya limited remedy to the aforementioned drawbacks. For this reason, aneed exists in the industry for improved IM systems that providesupplemental remedies to the aforementioned drawbacks.

SUMMARY

Preferred embodiments of the present disclosure provide for merging ofinstant messaging (IM) chat sessions into a single chat room. In someembodiments, an IM message from a second sender to the recipient isreceived while a first IM chat session has already been establishedbetween a first sender and the recipient. In response to receiving theIM message from the second sender, an IM chat room is establishedbetween the recipient, the first sender, and the second sender.

Other systems, methods, features, and advantages will be or becomeapparent to one with skill in the art upon examination of the followingdrawings and detailed description. It is intended that all suchadditional systems, methods, features, and advantages be included withinthis description.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the disclosure can be better understood with referenceto the following drawings. The components in the drawings are notnecessarily to scale, emphasis instead being placed upon clearlyillustrating the principles of the present invention. Moreover, in thedrawings, like reference numerals designate corresponding partsthroughout the several views.

FIG. 1 is a block diagram showing an embodiment of a system having amessage-handling instant messaging (IM) client.

FIG. 2 is a block diagram showing the workstation of FIG. 1 in greaterdetail.

FIG. 3A is a block diagram showing an embodiment having logic componentsof the message-handling IM client of FIGS. 1 and 2.

FIG. 3B is a block diagram showing another embodiment having logiccomponents of the message-handling IM client of FIGS. 1 and 2.

FIG. 4 is a flowchart showing an embodiment of a method forautomatically replying to IM messages when an IM recipient does notrespond for a predefined time interval.

FIG. 5 is a flowchart showing an embodiment of a method forautomatically replying to an IM message from a first IM sender when arecipient is engaged in an IM session with a second IM sender.

FIG. 6 is a flowchart showing an embodiment of a method for forwardingIM messages to a recipient at different IM clients.

FIG. 7 is a flowchart showing an embodiment of a method for transferringIM messages to a different recipient.

FIG. 8 is a flowchart showing an embodiment of a method for merging IMchat sessions.

FIG. 9 is a flowchart showing another embodiment of a method for mergingIM chat sessions.

FIG. 10A is a flowchart showing another embodiment of a method formerging IM chat sessions.

FIG. 10B is a flowchart showing another embodiment of a method formerging IM chat sessions.

FIG. 11A is a diagram showing an embodiment of a user interfaceassociated with the merging of IM chat sessions.

FIG. 11B is a diagram showing another embodiment of a user interfaceassociated with the merging of IM chat sessions.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Reference is now made in detail to the description of the embodiments asillustrated in the drawings. While several embodiments are described inconnection with these drawings, there is no intent to limit theinvention to the embodiment or embodiments disclosed herein. On thecontrary, the intent is to cover all alternatives, modifications, andequivalents.

While instant messaging (IM) systems have become increasinglysophisticated, several of the options available to telephone users arestill unavailable to IM users. In some instances, those optionsavailable for the telephone are unnecessary in IM environments due tothe very nature of the IM environment. For example, while a telephoneoften permits communications only between a caller and a callee, an IMrecipient may receive multiple IM messages from multiple senders whenthe IM recipient is logged on at an IM client.

Unfortunately, unlike telephones, which connect a caller to a calleeonly when a callee is physically able to pick up the telephone, IMpermits a sender to transmit an IM message to a recipient so long as therecipient has an accessible Internet presence (e.g., present andavailable) on IM, regardless of whether or not the recipient may bephysically present at the workstation. Thus, when an IM recipient hasstepped away from the workstation, any incoming IM message may bedisplayed without a reply from the recipient. In those instances, the IMsender often cannot discern whether the recipient has stepped away for abrief instance, or whether the recipient has chosen to ignore theincoming IM message, or whether the sender is on a “blacklist” (e.g.,ignore list, etc.).

It should be appreciated that the displaying of the message entails theexecution of a command from the processor to display the message. Inthis regard, even when the recipient cannot physically view the message,it should be understood that the message is “displayed” when theprocessor issues the command to display the message.

The term “presence” is used herein to indicate Internet presence, ratherthan physical presence, unless otherwise indicated. Hence, in order toavoid ambiguity, the term “physical presence” is explicitly usedthroughout this disclosure to denote physical presence, and the term“presence” is used to denote Internet presence (or online presence) asdefined in RFC 2778, RFC 2779, or other Internet-related documents.

In some embodiments, approaches are presented in which amessage-handling IM client may automatically respond to incoming IMmessages on behalf of a recipient. Unlike prior systems that globallyprovide a presence-status indication (also referred to herein as “statusindication” or, simply, “status,” e.g., available, away, busy,unavailable, etc.), the embodiments herein provide for amessage-by-message auto-reply. Hence, while prior systems provide timersthat track a user's activity at IM clients, the embodiments hereinprovide timing mechanisms that track elapsed times as a function ofreceived IM messages. Thus, in some embodiments, the timing mechanismtracks elapsed times from receipt of an IM message. In otherembodiments, the timing mechanism tracks elapsed times from a time ofdisplaying an IM message. In these several embodiments, the elapsed timeis calculated as a function of the specific IM message. Hence, ratherthan setting a global status that is visible to all potential senders,the message-handling IM client responds to each IM message on amessage-by-message basis.

In other embodiments, approaches are presented in which amessage-handling IM client may automatically forward incoming IMmessages to other IM addresses at which the recipient is present. Forexample, a recipient may concurrently be logged in using severaldifferent IM addresses (e.g., concurrently logged in at a workstationusing a first IM address (or account), a cellular telephone using asecond IM address, and a personal digital assistant (PDA) using a thirdIM address). In those instances, any incoming message to one of the IMaddresses may be forwarded to all of the other IM addresses at which therecipient is present.

In other embodiments, any incoming IM message may be forwarded toanother IM address at which the recipient was last active. In thisregard, if a recipient has been last active at an IM address at aworkstation, then any incoming IM to the recipient's PDA may beforwarded to the workstation. Similarly, any incoming IM to therecipient's cellular telephone may be forwarded to the workstation.Thus, for this embodiment, the message-handling IM client is configuredto direct any incoming IM message to the last-active location at whichthe recipient is present, thereby effectively following the recipient tothe recipient's most-recently-active IM address. Since the last-activetime is maintained by presence servers, the client may request thelast-active time from the server using known mechanisms.

In other embodiments, approaches are presented in which incoming IMmessages are transferred to another recipient. Hence, if a recipientreceives an IM message, and the recipient is unable to reply to themessage within a predefined time interval, then the message-handling IMclient transfers the received IM message to a third-person transferee.The transfer of the IM message establishes an IM chat session betweenthe sender and the transferee, rather than establishing an IM chatsession between the sender and the recipient. While the severalembodiments describe a recipient as receiving the IM message, it shouldbe appreciated that the IM message is received through an IM client. Inthis regard, phrases such as “recipient receives an IM message” shouldbe understood as being a shorthand notation for “recipient receives anIM message at the recipient's IM client.” Similarly, all actions (e.g.,transmit, forward, reply, etc.) attributed to users (e.g., sender,recipient, etc.) should be understood as being performed at an IM clientassociated with the corresponding user.

In other embodiments, approaches are presented in which two separate IMchat sessions are merged into a single IM chat session. For thoseembodiments, a recipient is already engaged in another IM session withan earlier sender. Thus, when a latter sender sends an IM message to therecipient, the latter sender is queried to determine whether or not thelatter sender wishes to join the IM chat session between the earliersender and the recipient. If the latter sender chooses to join the IMchat session between the earlier sender and the recipient, then therecipient is queried to determine whether or not the latter sender ispermitted to join the IM chat session between the earlier sender and therecipient. If the recipient approves, then the IM chat session betweenthe earlier sender and the recipient is merged with the IM chat sessionbetween the latter sender and the recipient. In other words, a single IMchat session (similar to a chat room) is established between the earliersender, the latter sender, and the recipient. The single IM chat sessionmay be established by using a recipient's IM client to bridge the chatsession between the earlier sender and the latter sender.

Several aspects of the various embodiments are described in greaterdetail with reference to FIGS. 1 through 11B.

FIG. 1 is a block diagram showing an embodiment of a system having amessage-handling instant messaging (IM) client 115 a . . . 115 c. Asshown in FIG. 1, one embodiment of an IM system includes IM-capabledevices 110, 120, 130, 140, 150, 160 that are communicatively coupled tothe Internet 160. The IM-capable devices may include workstations 110,140, 150, cellular telephones 120, personal digital assistants (PDA)130, or any other programmable device that may be configured to engagein IM communications. For purposes of illustration, the severalworkstations 110, 140, 150 are separately labeled as a senderworkstation 150, a recipient workstation 110, and a transfereeworkstation 140. Since both wired and wireless communication fromIM-capable devices to the Internet 160 are known in the art, only atruncated discussion of the actual device-to-Internet connection isprovided here.

In addition to the IM-capable devices 110, 120, 130, 140, 150, 160, thesystem further includes the Internet 160, which comprises a plurality ofservers 165, 170, 175. For purposes of illustration, the senderworkstation 150 is shown to be communicatively coupled to a senderserver 165; the recipient workstation 110 is shown to be communicativelycoupled to a recipient server 170; and the transferee workstation isshown to be communicatively coupled to the transferee server 175. Eachof the servers 165, 170, 175 are either directly or indirectly coupledto each other within the Internet 160. Since the communication betweenservers within the Internet are known in the art, further discussion ofserver-to-server communications is omitted here. Also, it should beappreciated that, while an example embodiment shows the Internet as thetransmission medium, other embodiments may be implemented in othernetworked environments.

Several examples are provided with reference to FIG. 1, in order toillustrate several embodiments of IM message handling by themessage-handling IM client 115 a . . . 115 c. Hardware details of thevarious IM-capable devices are shown with reference to FIGS. 2 through3B.

Using FIG. 1 to illustrate various embodiments of IM message handling,when a sender chooses to send an IM message to a recipient, the sendercomposes the IM message using the sender's IM client 155, which isrunning on the sender's workstation 150. Presuming that the recipient islogged in at a resource (e.g., workstation, cellular telephone, PDA,etc.), the composed IM message may be delivered to the recipient in nearreal-time. Since the determination of presence and their relatedstatuses are known in the art, only a truncated discussion of presenceand status determination is provided here. For example, when a user ispresent but unavailable, then the user's client provides an indicationof unavailability to the server, which subsequently broadcasts theunavailability to the contacts who are present on the Internet. Thecontacts' clients display the appropriate message to the contacts, inaccordance with methods known in the art.

Typically, the composed IM message at least includes information such asan intended recipient's IM address, the sender's IM address, and acontent of the IM message. Hence, in some embodiments, includingextensible markup language (XML)-based protocols, such as Jabber orother extensible messaging and presence protocol (XMPP) messagingprotocols, the IM message may include relevant XML tags that delineatethe sender, the recipient, and the body of the message. For example, anXMPP IM message in English, from juliet@capulet.com logged in at aresource (e.g., “balcony”), to romeo@montague.net, and having the text“Art thou not Romeo, and a Montague?” may appear as follows:

1 <message to=‘romeo@montague.net’ from=‘juliet@capulet.com/balcony’xml:lang=‘en’> <body>Art thou not Romeo, and a Montague?</body></message>

Typically, in XMPP, all of the information in the XML stream is suppliedby the client to the server. Hence, the server delivers the message fromthe sender to the recipient using the information in the XML stream. Inthis regard, once the IM message is transmitted from the sender'sworkstation 150 to the sender's server 165, the sender's server 165locates the recipient's server 170, which is communicatively coupled tothe recipient's workstation 110, at which the recipient is logged in.Thus, continuing with Romeo and Juliet's example above, when Julietdispatches the IM message “Art thou not Romeo, and a Montague?” from thesender workstation 150 (also referred to herein as “Juliet'sworkstation”), the IM message is conveyed to the sender's server 165(also referred to herein as “Juliet's server”). The sender's server 165receives the IM message and, using the “to” delineation in the XMLstream, locates the recipient's server 170 (also referred to herein as“Romeo's server”). Upon locating the recipient's server 170, the IMmessage is conveyed from the sender's server 165 to the recipient'sserver 170. The recipient's server 170 receives the IM message andfurther conveys the IM message to the recipient's workstation 110 (alsoreferred to herein as “Romeo's workstation”). The IM message is renderedand displayed to Romeo, who is logged in at the recipient's workstation110, by the message-handling IM client 115 a. While the followingexamples describe Romeo and Juliet as transmitting and receiving IM chatmessages, it should be appreciated that the IM chat messages, and theircorresponding commands and data, are transmitted and received throughRomeo and Juliet's respective message-handling IM clients. Hence, forexample, the phrase “Romeo receives a message” should be understood as ashorthand notation for “Romeo receives a message through Romeo'smessage-handling IM client.”

If Romeo is physically present at the recipient's workstation 110, andchooses to reply to Juliet, then the message-handling IM client 115 aconveys any reply from Romeo back to Juliet. Hence, again using an XMPPexample, if Romeo composes a message back to Juliet, saying “Neither,fair saint, if either thee dislike,” then this message may be XML-taggedto appear as:

2 <message to=‘juliet@capulet.com/balcony’from=‘romeo@montague.net/orchard’ xml:lang=‘en’> <body>Neither, fairsaint, if either thee dislike</body> </message>

The composed message by Romeo would then be transmitted from Romeo'sworkstation 110, cascaded through Romeo's server 170 and Juliet's server165, and received by Juliet's workstation 150. A chat session would,thereafter, continue between Romeo and Juliet. If, however, Romeo iseither not physically present at Romeo's workstation 110 or chooses notto reply to the IM message, then the message-handling IM client 115 amay execute a variety of options.

In some embodiments, if Romeo does not reply to Juliet's IM messagewithin a predefined time interval (e.g., within two minutes of receivingJuliet's IM message), the message-handling IM client 115 a at Romeo'sworkstation may provide an auto-reply to Juliet's IM message. Forexample, in some embodiments, a predefined message may be sent back toJuliet on behalf of Romeo by the message-handling IM client 115 a. Forexample, the predefined message may be a message that states “Romeo isunable to reply to your IM message at this moment.” For thoseembodiments in which the message-handling IM client 115 a provides anauto-reply, the message-handling IM client 115 a may generate an XMLstream similar to the following:

3 <message to=‘juliet@capulet.com/balcony’from=‘romeo@montague.net/orchard’ xml:lang=‘en’> <body>Romeo is unableto reply to your IM message at this moment.</body> </message>

The generated XML stream may be conveyed from Romeo's workstation 110back to Juliet's workstation 150 in a manner similar to that describedabove.

In some embodiments, the IM message may be transmitted periodically toJuliet at predefined time intervals. Thus, for example, the IM messagemay be transmitted back to Juliet every three minutes, thereby informingJuliet that Romeo has not yet returned to Romeo's workstation 110.

In other embodiments, if Romeo is logged in at several IM addressesusing several different resources (e.g., Romeo@montague.net on Romeo'sworkstation 110, Romeo@verona.it on Romeo's PDA 130, andRomeo@shakespeare.lit on Romeo's cellular telephone 120), then themessage-handling IM client 115 a may forward Juliet's IM message to eachof the resources at which Romeo is logged on. Thus, for example, ifJuliet's IM message is directed to Romeo@montague.net, then themessage-handling IM client 115 a at Romeo's workstation 110, whichcorresponds to Romeo's login under montague.net, receives the IMmessage.

Upon receiving the IM message from Juliet, if Romeo does not replywithin a predefined time interval (e.g., within one minute of receivingJuliet's IM message), then the message-handling IM client 115 adetermines whether or not Romeo is present in another domain at anotherresource, in accordance with known methods, as described in RFC 2778 and2779 and other known references. If the message-handling IM client 115 adetermines that Romeo is present in verona.it at Romeo's PDA 130, andalso present in shakespeare.lit at Romeo's cellular telephone 120, thenthe message handling IM client 115 a may generate the following XMLstreams:

4 <message to=‘romeo@verona.it’ from=‘juliet@capulet.com/balcony’xml:lang=‘en’> <body>Art thou not Romeo, and a Montague?</body></message> and: <message to=‘romeo@shakespeare.lit’from=‘juliet@capulet.com/balcony’ xml:lang=‘en’> <body>Art thou notRomeo, and a Montague?</body> </message>

The generated XML streams are then transmitted to Romeo's server 170,which conveys the forwarded message to Romeo at his various resources(e.g., PDA and cellular telephone). As shown here, in some embodiments,the “from” line in the message may reflect that Juliet sent the message,even though Romeo's message-handling IM client 115 a generated themessage. Hence, when Romeo replies from any of the resources at which heis present, an IM chat session is established between Romeo and Juliet,rather than being established between two of Romeo's IM resources.

In other embodiments, IM messages may be conveyed to Romeo'smost-recently-used IM address, rather than conveying the IM messages toall of Romeo's IM addresses. In doing so, the message-handling IM client115 a may determine Romeo's presence as well as the last active time ofRomeo at each of those resources. For those embodiments, themessage-handling IM client 115 a determines Romeo's presence using knownpresence mechanisms. Upon determining Romeo's presence, themessage-handling IM client 115 a ascertains a last active time of Romeoat each of Romeo's IM addresses at which he is present. Since theascertaining of last active times is known in the art, furtherdiscussion of ascertaining last-active-times is omitted here. Once thelast active times for all of Romeo's IM addresses have been ascertained,the message-handling IM client 115 a determines the most recent lastactive time. The IM message from Juliet is then conveyed to the IMaddress that corresponds to Romeo's most recent last active time. Hence,if Romeo was most-recently-active at montague.net on Romeo's workstation110, then Juliet's IM message, which originally arrived at Romeo'sworkstation 110, will not be forwarded to any of Romeo's other resourcessince Romeo's workstation 110 corresponds to the most recent last activetime. On the other hand, if Romeo was most-recently-active at verona.iton Romeo's PDA 130, then the message-handling IM client 115 a maygenerate and transmit the following XML stream:

5 <message to=‘romeo@verona.it’ from=‘juliet@capulet.com/balcony’xml:lang=‘en’> <body>Art thou not Romeo, and a Montague?</body></message>

Similarly, if Romeo was most-recently-active at shakespeare.lit onRomeo's cellular telephone 120, then the message-handling IM client 115a may generate and transmit the following XML stream:

6 <message to=‘romeo@shakespeare.lit’ from=‘juliet@capulet.com/balcony’xml:lang=‘en’> <body>Art thou not Romeo, and a Montague?</body></message>

As seen from these embodiments, Juliet's IM message follows Romeo toRomeo's most-recently-active resource, thereby resulting in a greaterprobability of actual IM communications between Romeo and Juliet.

In some embodiments, in addition to forwarding the IM message to Romeoat Romeo's other resources, the message-handling IM client 115 a mayalso generate an IM to Juliet to notify her that the IM message is beingforwarded to Romeo at another resource. In other embodiments, themessage-forwarding feature and the auto-reply feature may be combinedsuch that, rather than forwarding the message to Romeo's otherresources, an IM message may be transmitted back to Juliet to informJuliet that Romeo is currently logged on at another resource. That IMmessage may include Romeo's most-recently-active IM address, therebypermitting Juliet to send an IM directly to Romeo's most-recently-activeIM address.

In yet another embodiment, if Romeo does not reply to Juliet within apredefined time interval (e.g., within three minutes), then Juliet's IMmessage may be forwarded to another recipient at a transfereeworkstation 140. Thus, for example, Romeo may configure themessage-handling IM client 115 a to redirect all of the IM messages tomercutio@verona.it in the event that Romeo cannot immediately respond toincoming IM messages. Thus, for example, if Romeo again receives an IMmessage from Juliet, and does not respond within three minutes, then themessage-handling IM client 115 a may generate the following XML stream:

7 <message to=‘mercutio@verona.it’ from=‘juliet@capulet.com/balcony’xml:lang=‘en’> <subject>Auto-transfer of Message fromRomeo@montague.net</subject> <body>Art thou not Romeo, and aMontague?</body> </message>

As shown in this example, the XML stream may include a subject line thatindicates that the message has been automatically transferred toMercutio from Romeo. Additionally, the XML stream maintains Juliet's“from” address so that Mercutio may directly communicate with Julietusing IM, since the call has been transferred to Mercutio from Romeo.

In some embodiments, the message-handling IM client 115 a may requestpermission from Juliet prior to transferring her to Mercutio. For thoseembodiments, the message-handling IM client 115 a may reply back toJuliet using the following XML stream:

8 <message to=‘juliet@capulet.com/balcony’from=‘romeo@montague.net/orchard’ xml:lang=‘en’> <body>Romeo isunavailable at the moment. Would you like to continue the IM chatsession with Romeo's representative?</body> </message>

If Juliet indicates that she would like to continue in an IM chatsession with Romeo's representative, then the above message to Mercutiomay be transmitted to Mercutio by the message-handling IM client 115 a.Conversely, if Juliet indicates that she would not like to betransferred to Romeo's representative, then the message-handling IMclient 115 a may take no action.

In other embodiments, when Juliet indicates that she would like to betransferred, the message-handling IM client may convey Juliet's IMmessage to Mercutio and, also, identify Mercutio to Juliet, therebyspecifically informing Juliet that the IM message has been conveyed toMercutio. In this regard, the message-handling IM client may generateand convey two XML streams:

9 <message to=‘mercutio@verona.it’ from=‘juliet@capulet.com/balcony’xml:lang=‘en’> <subject>Auto-transfer of Message fromRomeo@montague.net</subject> <body>Art thou not Romeo, and aMontague?</body> </message> and: <messageto=‘juliet@capulet.com/balcony’ from=‘romeo@montague.net/orchard’xml:lang=‘en’> <body>Your IM message to Romeo has been transferred toMercutio.</body> </message>

In some embodiments, the message-handling IM client 115 a may merge twoor more independent IM chat sessions into a single IM chat session. Forexample, an IM chat session between Juliet and Mercutio may be mergedwith an IM chat session between Juliet and Romeo. The merging of the twoIM chat sessions results in a single IM chat session between Juliet,Romeo, and Mercutio. For those embodiments, Juliet may be engaged in anIM chat session with Romeo, when Mercutio sends an IM message to Juliet.Since Juliet is already engaged in the IM chat session with Romeo, themessage-handling IM client 115 a queries Mercutio to determine whetheror not Mercutio wishes to join the IM chat session that is already inprogress between Juliet and Romeo. In this regard, the message-handlingIM client 115 a generates and conveys an XML stream that identifies theIM chat session between Romeo and Juliet. The XML stream may appear as:

10 <message to=‘mercutio@verona.it’ from=‘juliet@capulet.com/balcony’xml:lang=‘en’> <body>Juliet is currently engaged in an IM chat sessionwith Romeo. Do you wish to join Romeo and Juliet's IM chatsession?</body><thread>e0ffe42b8561960c6b12b944a0927-94b9683a38</thread> </message>

In the event that Mercutio has a message-handling IM client 115 b, thatIM client may display the query in the form of a dialogue box withuser-selectable options, or other known graphical user interfaces (GUI).In the event that Mercutio has a conventional IM client, the query mayappear as a standard IM chat message. Hence, when Mercutio replies tothat IM chat message, Juliet's message-handling IM client 115 a may beconfigured to process the reply from Mercutio. The components associatedwith prompting Mercutio are described in greater detail below.

Upon being queried, if Mercutio indicates that he wishes to join Romeoand Juliet's IM chat session by, for example, providing input at theGUI, then the message-handling IM client 115 a queries Juliet todetermine whether or not Mercutio is welcome to join Romeo and Juliet'sIM chat session. An XML stream for such a query may appear as:

11 <message to=‘juliet@capulet.com/balcony’from=‘juliet@capulet.com/balcony’ xml:lang=‘en’> <body>Mercutio hasrequested to participate in the IM chat session between you andRomeo</body> <thread>e0ffe42b8561960c6b12b944a092794b9683a38</thread></message>

If Juliet approves of Mercutio's participation, then a three-way IM chatsession is established between Juliet, Romeo, and Mercutio. In someembodiments, Mercutio may be a contact on the IM roster for both Romeoand Juliet. For other embodiments, Mercutio need not be a contact oneither IM roster. For yet other embodiments, Mercutio may be a contacton either Romeo's IM roster or Juliet's IM roster. Similarly, theembodiments disclosed herein may be independent of whether or notvarious communicants are listed as contacts on the other communicants'IM rosters.

Also, for some embodiments, Mercutio's exchange with Juliet may berevealed to Romeo. Conversely, for other embodiments, Mercutio'sexchange with Juliet may be hidden from Romeo. It should be appreciatedthat the various permutations that are possible are within the technicalcompetence of one having ordinary skill in the art. Hence, the plethoraof permutations in implementing the message-handling IM client 115 a isomitted here.

Optionally, for other embodiments, the message-handling IM client 115 amay query both Juliet and Romeo to determine whether or not Romeo, aswell as Juliet, wishes to include Mercutio in the IM chat session. Inthis regard, the XML stream may appear as:

12 <message to=‘juliet@capulet.com/balcony’to=‘romeo@montague.net/orchard’ from=‘juliet@capulet.com/ba-lcony’xml:lang=‘en’> <body>Mercutio has requested to participate in the IMchat session between you and Romeo</body><thread>e0ffe42b8561960c6b12b944a092794b-9683a38</thread> </message>

For those embodiments, if both Romeo and Juliet approve of Mercutio'sparticipation, then a three-way IM chat session may be establishedbetween Juliet, Romeo, and Mercutio. In other embodiments, if eitherRomeo alone, or Juliet alone, approves of Mercutio's participation, thena three-way IM chat session may be established between Juliet, Romeo,and Mercutio.

The three-way IM chat session may be seen as a merging of two separateIM chat sessions: the IM chat session between Juliet and Romeo (an IMchat session that is already in progress), and the IM chat sessionbetween Juliet and Mercutio (a newly-established IM chat session). Oncethe three-way IM chat between Juliet, Romeo, and Mercutio isestablished, for example, by reflecting all messages from Juliet, Romeo,and Mercutio to all of the participants, the three participants maycontinue in their joint chat session as if they were participating in aprivate chat room. Since exchanging of messages in chat room is known inthe art, further discussion of the three-way chat is omitted here.

As shown from the embodiments above, by providing auto-reply mechanisms,auto-forwarding mechanisms, auto-message-transfer mechanisms, and IMchat-session merging mechanisms, the message-handling IM client 115 aprovides greater versatility in IM communications than previouslyavailable.

FIG. 2 is a block diagram showing the workstation of FIG. 1 in greaterdetail. Since the embodiments above show Romeo's workstation 110 ashandling all auto-replies, auto-forwards, and auto-message-transfers,only the components of the workstation 110 are shown in FIG. 2. However,it should be appreciated that the PDA 130 and the cellular telephone 120may also include a similar component architecture.

As shown in FIG. 2, the recipient workstation 110 comprises a systemboard that includes a processor 220, a network interface 250, a memory230, a local storage device 240, and a bus 210 that permitscommunication between the various components. In one example, the localstorage device 240 may be a hard drive configured to electronicallystore data. The local storage device 240 may also store computerprograms that execute on the recipient workstation 110. In this sense,the processor 220 is configured to access any program that is stored onthe local storage device 240, and execute the program with theassistance of the memory 230. As shown in FIG. 2, the memory 230, in oneembodiment, includes a message-handling IM client 115 a. Since thefunctioning of computing devices is well known in the art, furtherdiscussion of the processor 220, the memory 230, and the local storagedevice 240 are omitted here. Also, since various functions of themessage-handling IM client 115 a are discussed in great detail withreference to FIG. 1, further details of the message-handling IM client115 a are omitted here. While the various components are shown asresiding on a single system board, it will be clear to one of ordinaryskill in the art that the various components may reside at differentlocations, so long as they are coupled to each other to allowcommunication between the components.

The network interface 250 of FIG. 2 is configured to provide aninterface between the recipient workstation 110 and the server hardware165, 170, 175 in the Internet 160. Thus, the network interface 250provides the interface for the recipient workstation 110 to receive anydata that may be entering from the Internet 160 and, also, to transmitany data from the recipient workstation 110 to the Internet 160. In thisregard, the network interface 250 may be a modem, a network card, or anyother interface that interfaces the recipient workstation 110 to anetwork.

FIG. 3A is a block diagram showing, in greater detail, an embodiment ofthe message-handling IM client 115 a of FIGS. 1 and 2. In this regard,FIG. 3A dissects the various functions of one embodiment of themessage-handling IM client 115 a of FIG. 1 into its correspondingstructural components. As shown in FIG. 3A, the message-handling IMclient 115 a comprises IM receive logic 305, display logic 310, timinglogic 315, prompting logic 320, presence logic 325, and convey logic330.

The IM receive logic 305 is adapted to receive and process incoming IMmessages. Hence, when Juliet sends an IM message to Romeo, the IMreceive logic 305 receives Juliet's IM message and processes the IMmessage. The display logic 310 is configured to display the received andprocessed IM message. Hence, the display logic 310 renders Juliet's IMmessage for display on Romeo's workstation 110. In some embodiments, thereceiving of Juliet's IM message and the displaying of Juliet's IMmessage happen substantially contemporaneously. It should be appreciatedthat the displaying of the IM message refers to any one of: displayingthe IM chat window, displaying a minimized IM chat window and acorresponding icon for the IM chat window, displaying a visualindication of a received IM message, etc.

The timing logic 315 tracks the elapsed time from when Juliet's IMmessage is displayed for Romeo. In this regard, for some embodiments,the timing logic 315 also serves as a trigger for any auto-replying,auto-forwarding, or auto-transferring of Juliet's IM messages. As isknown in the art, the default time for triggering such events may be setby the user or may be hard-coded into the message-handling IM client 115a. Since the setting of such user preferences is known in the art,further discussion of the setting of user preferences is omitted here.

The prompting logic 320 is configured to prompt the user for additionalinput. For example, in the auto-forwarding embodiments described above,the prompting logic 320 is configured to prompt Juliet for input onwhether or not Juliet wishes to forward her IM message to Romeo's otherIM addresses. In the auto-transferring embodiments, the prompting logic320 is configured to prompt Juliet to determine whether or not Julietwishes to be transferred to Mercutio.

The presence logic 325 is configured to determine Romeo's presence atall of Romeo's IM addresses. Additionally, the presence logic 325 isconfigured to determine the presence of all of Romeo's IM contacts.Presence is determined using a variety of known presence mechanisms,which are not discussed herein.

The convey logic 330 is configured to convey the generated XML streamsfrom the workstation 110 to the various intended recipients (e.g.,Juliet and Mercutio). In this regard, the convey logic 330 may furtherbe seen as comprising indicator messages 360, message reply logic 340,message transfer logic 345, message forward logic 350, and IM addressappend logic 355. Additionally, the message-handling IM client 115further comprises IM addresses 335 for Romeo's other IM accounts.

The message reply logic 340 is configured to generate and convey anauto-reply message in response to receiving an IM message from a sender.The message transfer logic 345 is configured to generate and convey allIM messages that may be used in the event that an incoming IM message istransferred to a transferee. The message forward logic 350 is configuredto determine the presence of the recipient at all of the recipient's IMaddresses, and, also, to determine the last active time for each ofthose IM addresses. Additionally, the message forward logic 350 isconfigured to generate and convey all IM messages that may be used inthe event that an incoming IM message is forwarded to another of therecipient's IM addresses.

The indicator messages 360 include all messages that are used ingenerating the XML streams. Thus, for example, the indicator messages360 may include an auto-reply message that reads, for example, “Romeo iscurrently unavailable to reply to your IM message.” For auto-forward,the indicator messages 360 may read “Romeo has most recently been activeat romeo@verona.it” or “Your message is being forwarded to Romeo atromeo@verona.it.” For auto-transferring, the indicator messages may read“Your message is being forwarded to Mercutio.” While not explicitlyprovided, it should be appreciated that any message to be included inthe auto-message-handling process may be stored as one of the indicatormessages 360.

The IM address append logic 335 is configured to append the proper IMaddress to generated IM messages. Thus, for example, if an auto-replymessage is generated, then the IM address append logic 335 is configuredto append the original sender's IM address to theautomatically-generated IM message. In the above example, if anauto-reply is generated in response to Juliet's IM message, then the IMaddress append logic 335 will append Juliet's IM address to thegenerated auto-reply message.

Similarly, if an auto-forward message is generated, then, for someembodiments, the IM address append logic 335 is configured to append allof Romeo's present IM addresses to each of the generated IM messages.For other embodiments, the IM address append logic 335 is configured toappend Romeo's most-recently-active IM address to the generated IMmessage.

For auto-transferring embodiments, the IM address append logic 335 isconfigured to append the transferee's IM address to the generated IMmessage. For example, if Mercutio is the transferee, then the IM addressappend logic 335 appends Mercutio's IM address to the generated IMmessage.

As shown in the embodiment of FIG. 3A, the message-handling IM client115 comprises structural components that are configured to perform thevarious IM functions as described with reference to FIG. 1, and, also,to perform various conventional IM functions. Moreover, as shown inFIGS. 1 through 3B, systems with added functionality in handling IMmessages provide a more versatile IM environment.

Having described several embodiments of systems for handling IMmessages, attention is turned to FIGS. 4 through 10B, which describeseveral embodiments of methods for handling IM messages. While themethods of FIGS. 4 through 10B may be implemented by the systemsdescribed in FIGS. 1 through 3B, it should be appreciated that othersystems may be used to implement the processes of FIGS. 4 through 10B,and, hence, the processes of FIGS. 4 through 10B are not limited to thesystems of FIGS. 1 through 3B.

FIG. 3B is a block diagram showing, in greater detail, an embodiment ofthe message-handling IM client 115 a of FIGS. 1 and 2. In this regard,FIG. 3B dissects the various functions of one embodiment of themessage-handling IM client 115 a of FIG. 1 into its correspondingstructural components. As shown in FIG. 3B, the message-handling IMclient 115 a comprises IM receive logic 307, display logic 312,session-tracker logic 317, sender-query logic 322, recipient-query logic332, merge-determination logic 327, IM chat-session-merge logic 337, andchat-room logic 342.

The IM receive logic 307 is adapted to receive and process incoming IMmessages. Hence, when Juliet sends an IM message to Romeo, the IMreceive logic 307 receives Juliet's IM message and processes the IMmessage. The display logic 312 is configured to display the received andprocessed IM message. Hence, the display logic 312 renders Juliet's IMmessage for display on Romeo's workstation 110. In some embodiments, thereceiving of Juliet's IM message and the displaying of Juliet's IMmessage happen substantially contemporaneously.

The session-tracker logic 317 is adapted to track ongoing chat sessionsestablished by the message-handling IM client 115 b. In this regard, thesession-tracker logic 317 determines whether or not the recipient isengaged in one or more IM chat sessions with one or more senders. Thus,for example, if Juliet (recipient) is engaged in an IM chat session withRomeo (one sender) as well as with Mercutio (another sender), then thesession-tracker logic 317 keeps track of those IM chat sessions. Inother words, the session-tracker logic 317 tracks whether the IM chatsession between Juliet and Romeo has terminated or is continuing.Similarly, the session-tracker logic 317 tracks whether the IM chatsession between Juliet and Mercutio is continuing or has terminated.

The sender-query logic 322 is adapted to send appropriate queries to oneor more senders. Thus, for example, when the message-handling IM client115 b determines that a sender is to be provided with an invitation tojoin an IM chat session already in progress, the sender-query logic 322generates the appropriate invitation Similarly, the recipient-querylogic 332 is adapted to send appropriate queries to the recipient. Thus,for example, when the message-handling IM client 115 b receives arequest to join an IM chat session from a sender, the recipient-querylogic 332 queries the recipient for permission to include the sender inan IM chat session already in progress.

The merge-determination logic 327 collects and compiles the replies thatare received in response to the queries generated by the sender-querylogic 322 and the recipient-query logic 332. Thus, for example, when thesender-query logic 322 generates an invitation to the sender to join analready-established IM chat session, and the sender replies to theinvitation, the merge-determination logic 327 determines whether or notsender has accepted or rejected the invitation. This determination maybe accomplished by processing input provided by a sender at, forexample, a GUI at the sender's IM client, and received by themessage-handling IM client 115 a of the recipient. Similarly, when therecipient-query logic 332 queries the recipient for permission toinclude the sender in the already-established IM chat session, and therecipient replies to the query, the merge-determination logic 327determines whether or not the recipient has granted permission or deniedpermission to the sender. This determination is accomplished byprocessing input that may be provided by the recipient. Thus, themerge-determination logic 327 compiles the replies from both the senderand the user to determine whether or not IM chat sessions should bemerged together.

The IM chat-session-merge logic 337 merges multiple IM chat sessionsinto a single IM chat session in response to the merge-determinationlogic 327 determining that the IM chat sessions should be merged. Inthis regard, the IM chat-session-merge logic 337 gathers informationneeded to convert multiple chat sessions into a single IM chat room. Insome embodiments, this information includes sender IM information foreach of the senders, the recipient's IM information, and IM threadinformation.

The chat-room logic 342 is adapted to convert an IM chat session betweena sender and a recipient into an IM chat room between the recipient andmultiple senders. In this regard, the information gathered by the IMchat-session-merge logic 337 is combined so that the messages from allof the participants are reflected to all of the other participants. Thevarious functions corresponding to the IM receive logic 307, the displaylogic 312, the session-tracker logic 317, the sender-query logic 322,the recipient-query logic 332, the merge-determination logic 327, the IMchat-session-merge logic 337, and the chat-room logic 342 are discussedbelow with reference to FIGS. 8 through 10B.

As shown in the embodiment of FIG. 3B, the message-handling IM client115 comprises structural components that are configured to perform thevarious IM functions as described with reference to FIG. 1, and, also,to perform various conventional IM functions. Moreover, as shown inFIGS. 1 through 3B, systems with added functionality in handling IMmessages provide a more versatile IM environment. As with FIG. 3A, thestructures as shown are not indicative of programming logical structuresin all embodiments.

Having described several embodiments of systems for handling IMmessages, attention is turned to FIGS. 4 through 10B, which describeseveral embodiments of methods for handling IM messages. While themethods of FIGS. 4 through 10B may be implemented by the systemsdescribed in FIGS. 1 through 3B, it should be appreciated that othersystems may be used to implement the processes of FIGS. 4 through 10B,and, hence, the processes of FIGS. 4 through 10B are not limited to thesystems of FIGS. 1 through 3B.

FIG. 4 is a flowchart showing an embodiment of a method forautomatically replying to IM messages when an IM recipient does notrespond for a predefined time interval. As shown in FIG. 4, anembodiment of the process begins when an IM message from a sender isreceived (410) by a recipient. The received IM message is then displayed(420) to the recipient. In some embodiments, the IM message may berendered and displayed by a message-handling IM client 115 a similar tothat shown in FIGS. 1 through 3B. Upon displaying the IM message, the IMsystem waits (430) for a predefined time interval for any response fromthe recipient. In some embodiments, the system waits a predefined timeinterval for the recipient to reply to the displayed IM message. Whenthe predefined time interval elapses, the system determines (440)whether or not there has been a response to the received IM message fromthe recipient. If there has been a response by the recipient, then an IMchat session is established (450) between the sender of the IM messageand the recipient. If, on the other hand, no response has been providedby the recipient during the time interval, then a message, whichindicates that the recipient is unavailable to engage in an IM chatsession, is provided (460). This message is transmitted to the sender.Additionally, a message, which requests the sender to wait for apredetermined time interval, may also be provided (470) and alsotransmitted to the sender. In some embodiments, the messages may be XMLstreams that are decipherable by IM clients. As such, the messagesprovided to the recipient may be, for example:

13 <message to=‘sender@sdomain.com/sresource’from=‘recipient@rdomain.com/rresource’ xml:lang=‘en’> <body>AUTO-REPLYMESSAGE FROM RECIPIENT TO SENDER</body> </message>

It should be appreciated that the auto-reply message included in thebody of the IM message may be custom-tailored by the auto-replier.

FIG. 5 is a flowchart showing another embodiment of a method forautomatically replying to an IM message from a first IM sender when arecipient is engaged in an IM session with a second IM sender. For thisembodiment, the process begins when an IM message from a sender isreceived (510) by a recipient. The received IM message is then displayed(520) to the recipient, and, thereafter, the system waits (530) apredefined time interval for any response from the recipient. After thepredefined time interval elapses, the system determines (540) whether ornot the recipient has provided any response to the displayed IM message.If the recipient has provided a response, then the an IM chat session isestablished (550) between the sender of the IM message and the recipientof the IM message. If, on the other hand, no response has been providedto the displayed IM message, then the system further determines (560)whether or not the recipient is already engaged in an IM chat sessionwith another IM contact. If the recipient is not already engaged inanother IM chat session with another IM contact, then a message, whichindicates that the recipient is unavailable to engage in an IM chatsession with the sender, is provided (570) to the sender of the IM chatmessage. Additionally, another message, which requests the sender towait for a predefined time interval, may also be provided (590). Uponproviding (570, 590) messages to the sender, the process repeats fromthe waiting step (530). If the recipient, however, is already engaged inan IM chat session with another IM contact, then a message, whichindicates that the recipient is already engaged in an IM chat sessionwith another IM contact, is provided (580) to the sender. Thereafter, amessage, which requests the sender to wait for a predetermined timeinterval, may also be provided (590) to the sender. Upon providing (580,590) the messages to the sender, the process repeats from the waitingstep (530). Similar to the embodiment of FIG. 4, the messages providedto the sender may be composed and embedded in XML streams, therebypermitting deciphering by the sender's IM client.

FIG. 6 is a flowchart showing an embodiment of a method for forwardingIM messages to a recipient at different IM clients. In some embodiments,the message-forwarding process may begin when an IM message from asender is received (610) by a recipient who has multiple IM addresses.Upon receiving the IM message, one of the multiple IM addresses isselected (620). Thereafter, the system determines (630) whether or notthe recipient is present at the selected IM address.

If it is determined (630) that the recipient is present at the selectedIM address, then the system ascertains (640) the last-active time forthe selected IM address. The system then determines (650) whether or notthe selected IM address has the most recent last active time. If it isdetermined that, of those IM addresses in which last active times havebeen ascertained, the selected IM address has the most recent lastactive time, then the selected IM address is stored as the target IMaddress, and the system proceeds to determine (670) whether or not allIM addresses have been checked for presence and last active time. If allIM addresses have been checked for presence and last active time, thenthe system further determines (685) whether or not amost-recently-active IM address has been stored. If amost-recently-active IM address has been stored, then an IM message isconveyed (690) to the stored, most-recently-active IM address. If no IMaddress has been stored, then the process terminates without conveyingany IM messages.

It should be appreciated that the most-recently-active IM address mayalso be used in conjunction with other presence criteria to determineproper routing of the IM message. For example, if themost-recently-active IM address has a presence setting that isindicative of unavailability (e.g., “extended away,” “do not disturb,”etc.), then the process, in some embodiments, may disregard themost-recently-active IM address due to the presence setting that conveysunavailability of the recipient at that IM address. In this regard, forsome embodiments, the most-recently-active IM address may be seen as themost-recently-active IM address at which the recipient is indicated asbeing available.

Returning to the determination (670) of whether or not all IM addresseshave been checked, if the system determines (670) that all of therecipient's IM addresses have not been checked, then the system selects(680) another IM address and again determines (630) whether or not therecipient is present at the selected IM address. Thereafter, the processcontinues as described above.

Continuing with the determination (650) of the most recent last activetime, if it is determined (650) that the selected IM address does nothave the most recent last active time, then the system proceeds, withoutstoring the selected IM address, to determine (670) whether or not allIM addresses have been checked, and the process continues as describedabove.

Returning to the presence-determining step (630), if it is determined(630) that the recipient is not present at the selected IM address, thenthe system proceeds to determine (670) whether or not all of therecipient's IM addresses have been checked for presence. If all of therecipient's IM addresses have been checked for presence, and the processcontinues as described above.

As shown in FIG. 6, if an IM recipient is concurrently logged in at manydifferent resources under many different IM accounts, the received IMmessage may be conveyed to the recipient's most-recently-active IMaddress. The conveying of the IM message to the most-recently-active IMaddress permits the sender to follow the IM recipient as the recipient'sIM activity switches from one resource to another resource. While notexplicitly shown in FIG. 6, it should be appreciated that, rather thanconveying the IM message to one most-recently-active IM address, the IMmessage may be conveyed to all of the recipient's IM addresses at whichthe user may, or may not, be present. This type of “shotgun” approachensures the sender that the recipient will most likely receive the IM atone of the recipient's IM addresses.

While not explicitly shown in FIG. 6, it should be appreciated that thesender may be prompted for permission to forward the IM message prior toforwarding the IM message. In this regard, the process may include aprompting step that is similar to that shown below in FIG. 7. For thoseembodiments that request permission from the sender, the process mayfurther provide an option for the sender to convey the IM message to theoriginally-designated IM address and mark the IM message as being“urgent.” This option may be provided in the form of user-selectableentries in a graphical user interface or other technically-feasible userinterfaces, which are known in the art. Alternatively, this option maybe implemented by supplying an additional comment line to the sender.

While the embodiment of FIG. 6 shows the IM message being forwarded toone of the recipient's IM addresses, it should be appreciated that theIM message may be routed to the recipient without utilizing the presencetransport of IM. For example, rather than determining the recipient'spresence, the IM message may be forwarded to the recipient's cellulartelephone via a short message service (SMS) protocol, which is known inthe art. Similarly, the IM message may also be converted to speech andconveyed as a voice mail message using known text-to-speech protocols.In this regard, it should be appreciated that the IM message may beencapsulated for transport in any known medium, thereby permitting asender to convey the IM message to the recipient using non-IM transportmechanisms. Since non-IM transport media are known in the art, furtherdiscussion of non-IM transport media are not discussed further.Additionally, it should be appreciated that known mechanisms may be usedfor transporting the substance of the IM messages on the correspondingtransport medium. Since various text-transport mechanisms are known inthe art, further discussion of text-transporting mechanisms is omittedhere.

In some embodiments, the IM message may be forwarded by amessage-handling IM client 115 similar to that shown in FIGS. 1 through3B. For those embodiments, the message-handling IM client 115 appendsthe sender's IM information to the forwarded IM message, therebypermitting the recipient to establish an IM chat session from any of therecipient's IM resources from which the recipient is logged on.

FIG. 7 is a flowchart showing an embodiment of a method for transferringIM messages to a different recipient. In some embodiments, themessage-transferring process begins when an IM message from a sender isreceived (705) by a recipient (also referred to herein as a firstrecipient). The received IM message is then rendered and displayed (710)to the first recipient. Thereafter, the system waits (715) apredetermined time interval for the first recipient to provide anyresponse to the displayed IM message. Upon expiration of thepredetermined time interval, the system determines (720) whether or notthere has been any response (or input) from the first recipient. If thefirst recipient has responded, then an IM chat session is established(725) between the sender of the IM message and the first recipient.

If, on the other hand, no input has been provided by the firstrecipient, then the system prompts (730) the sender for permission toconvey the IM message to a transferee (also referred to herein as asecond recipient). When the sender provides a response to the prompt,the system receives (735) the response and determines (740) whether ornot the response indicates a granting or denial of permission totransfer the IM message. If the response is a denial of permission totransfer the IM message, then the process terminates. On the other hand,if the response is a granting of permission to transfer the IM message,then the IM message is conveyed (745) to the second recipient. Inaddition to conveying (745) the IM message, the system may also indicate(750) to the second recipient that the IM message originated from thesender, rather than originating from the first recipient.

In some embodiments, the process of FIG. 7 may be performed by themessage-handling IM client 115 as shown in FIGS. 1 through 3B. Hence,for those embodiments, the transferred message may be embedded in an XMLstream similar to, for example:

14 <message to=‘transferee@tdomain.com/tresource-’ from=‘sender@sdomain.com/sresource’ xml:lang=‘en’> <body>AUTO-TRANSFER OF MESSAGECOMPOSED BY SENDER AND ORIGINALLY DELIVERED TO RECIPIENT</body></message>

FIG. 8 is a flowchart showing an embodiment of a method for merging IMchat sessions. The process of merging IM chat sessions occurs in anenvironment where a recipient is already engaged in an IM chat sessionwith an earlier sender. Thus, in some embodiments, the process beginswhen an IM message from a latter sender is received (805) at amessage-handling IM client 115 deployed by the recipient. Upon receiving(805) the IM message from the latter sender (hereinafter also referredto as “latter IM message”), the message-handling IM client 115determines (810) whether or not the recipient is engaged in an IM chatsession with an earlier sender. If it is determined (810) that therecipient is not already engaged in an IM chat session, then the processends.

Conversely, if it is determined (810) that the recipient is alreadyengaged in an IM chat session with an earlier sender, then themessage-handling IM client 115 queries (815) the latter sender todetermine whether or not the latter sender wishes to join the IM chatsession already in progress. In some embodiments, the query may be apop-up window that is displayed at the latter sender's IM client. Inother embodiments, the query may be an automatically generated reply tothe latter sender's IM message. In the query, the message-handling IMclient 115 asks the latter sender whether or not the latter senderwishes to join the IM chat session between the recipient and the earliersender, which is already in progress. When the latter sender replies tothe query, the message-handling IM client 115 receives (820) the replyand determines (825) whether or not the latter sender has requested tojoin the IM chat session between the earlier sender and the recipient.If the message-handling IM client 115 determines (825) that the lattersender does not wish to join the IM chat session already in progress,then the process ends.

Alternatively, if the message-handling IM client 115 determines (825)that the latter sender wishes to join the IM chat session already inprogress, then the message-handling IM client 115 queries (830) therecipient for approval to include the latter sender in the IM chatsession already in progress. In some embodiments, the query may be apop-up window generated at the recipient's message-handling IM client115. When the recipient replies to the query, the message-handling IMclient 115 receives (835) the query and determines (840) whether or notthe recipient has approved the request by the latter sender to join theIM chat session already in progress. If the recipient rejects therequest, then the process ends. If, however, the recipient approves therequest, then an IM chat session is established (845) between theearlier sender, the latter sender, and the recipient.

Using the example of Romeo and Juliet, the process of FIG. 8 mayprogress as follows. Initially, an IM chat session is establishedbetween Romeo (earlier sender) and Juliet (recipient). During this IMchat session, Mercutio (latter sender) sends an IM message to Juliet. Inresponse to Mercutio's IM message, Juliet's message-handling IM client115 determines that Juliet is already engaged in an IM chat session withRomeo. Thus, Juliet's message-handling IM client 115 queries Mercutio todetermine whether or not Mercutio wishes to join the IM chat sessionalready in progress between Juliet and Romeo. When Mercutio provides anindication that he wishes to join the IM chat session, Juliet'smessage-handling IM client 115 conveys that indication to Juliet. WhenJuliet approves of Mercutio's participation in the IM chat session, theIM chat session is opened up to Mercutio. Thus, a three-way IM chatsession is established between Romeo, Juliet, and Mercutio.

FIG. 9 is a flowchart showing another embodiment of a method for mergingIM chat sessions. Similar to FIG. 8, the process of merging IM chatsessions in FIG. 9 occurs in an environment where a recipient is alreadyengaged in an IM chat session with an earlier sender. Thus, in someembodiments, the process begins when an IM message from a latter senderis received (905) at a message-handling IM client 115 deployed by therecipient. Upon receiving (905) the latter IM message, themessage-handling IM client 115 determines (910) whether or not therecipient is already engaged in an IM chat session with an earliersender. If it is determined (910) that the recipient is not alreadyengaged in an IM chat session, then the process ends.

If, however, it is determined (910) that the recipient is alreadyengaged in an IM chat session with an earlier sender, then themessage-handling IM client 115 queries (915) the recipient for approvalto include the latter sender in the IM chat session already in progress.In some embodiments, the query may be a pop-up window that is displayedat the recipient's IM client. In the query, the message-handling IMclient 115 asks the recipient whether or not the latter sender may jointhe IM chat session between the recipient and the earlier sender, whichis already in progress. When the recipient replies to the query, themessage-handling IM client 115 receives (920) the reply and determines(925) whether or not the recipient has approved the participation of thelatter sender in the IM chat session already in progress. If themessage-handling IM client 115 determines (925) that the recipient hasrejected the participation of the latter sender in the IM chat sessionalready in progress, then the process ends.

Alternatively, if the message-handling IM client 115 determines (925)that the recipient has approved the participation of the latter IMsender in the IM chat session already in progress, then themessage-handling IM client 115 also queries (930) the earlier sender forapproval to include the latter sender in the IM chat session. In someembodiments, the query may be a pop-up window at the earlier sender'smessage-handling IM client 115. In other embodiments, the query may bean IM message text line in the IM chat session. Hence, for embodimentsemploying the IM message text line, the query (915) to the recipient andthe query (930) to the earlier sender may occur concurrently. When theearlier sender replies to the query, the message-handling IM client 115receives (935) the query and determines (940) whether or not the earliersender has approved the request by the latter sender to join the IM chatsession already in progress. If the earlier sender has rejected therequest, then the process ends. If, however, the earlier sender hasapproved the request, then an IM chat session is established (945)between the earlier sender, the latter sender, and the recipient.

Using the example of Romeo and Juliet, the process of FIG. 9 mayprogress as follows. Initially, an IM chat session is establishedbetween Romeo (earlier sender) and Juliet (recipient). During this IMchat session, Mercutio (latter sender) sends an IM message to Juliet. Inresponse to Mercutio's IM message, Juliet's message-handling IM client115 determines that Juliet is engaged in an IM chat session with Romeo.Thus, Juliet's message-handling IM client 115 queries Juliet todetermine whether or not Mercutio is welcome to join the IM chat sessionalready in progress between Juliet and Romeo. When Juliet provides anindication that Mercutio is welcome to join the IM chat session,Juliet's message-handling IM client 115 displays a similar request toRomeo. When Romeo approves of Mercutio's participation in the IM chatsession, a three-way IM chat session is established between Romeo,Juliet, and Mercutio.

FIG. 10A is a flowchart showing another embodiment of a method formerging IM chat sessions. Similar to FIGS. 8 and 9, the process ofmerging IM chat sessions in FIG. 10A occurs in an environment where arecipient is already engaged in an IM chat session with an earliersender. Thus, in some embodiments, the process begins when an IM messagefrom a latter sender is received (1005) at a message-handling IM client115 deployed by the recipient. Upon receiving (1005) the latter IMmessage, the message-handling IM client 115 determines (1010) whether ornot the recipient is engaged in an IM chat session with an earliersender. If it is determined (1010) that the recipient is not alreadyengaged in an IM chat session, then the process ends.

Alternatively, if it is determined (1010) that the recipient is alreadyengaged in an IM chat session with an earlier sender, then themessage-handling IM client 115 queries (1015) the recipient for approvalto include the latter sender in the IM chat session already in progress.In some embodiments, the query may be a pop-up window that is displayedat the recipient's message-handling IM client. In other embodiments, thequery may be an IM message text line that appears in the message windowat the recipient's message-handling IM client 115. In the query, themessage-handling IM client 115 asks the recipient whether or not thelatter sender may join the IM chat session between the recipient and theearlier sender, which is already in progress. When the recipient repliesto the query, the message-handling IM client 115 receives (1020) thereply and determines (1025) whether the recipient has approved orrejected the participation of the latter sender in the IM chat sessionalready in progress. If the message-handling IM client 115 determines(1025) that the recipient has rejected the participation of the lattersender in the IM chat session already in progress, then the processends. If, however, the recipient has approved the latter sender'sparticipation, then a three-way IM chat session is established (1045)between the earlier sender, the latter sender, and the recipient.

Using the example of Romeo and Juliet, the process of FIG. 10A mayprogress as follows. Initially, an IM chat session is establishedbetween Romeo (earlier sender) and Juliet (recipient). During this IMchat session, Mercutio (latter sender) sends an IM message to Juliet. Inresponse to Mercutio's IM message, Juliet's message-handling IM client115 determines that Juliet is engaged in an IM chat session with Romeo.Thus, Juliet's message-handling IM client 115 queries Juliet todetermine whether or not Mercutio is welcome to join the IM chat sessionalready in progress between Juliet and Romeo. When Juliet provides anindication that Mercutio is welcome to join the IM chat session, athree-way IM chat session is established between Romeo, Juliet, andMercutio.

FIG. 10B is a flowchart showing another embodiment of a method formerging IM chat sessions. Similar to FIGS. 8 through 10A, the process ofmerging IM chat sessions in FIG. 10A occurs in an environment where arecipient is already engaged in an IM chat session with an earliersender. Thus, in some embodiments, the process begins when an IM messagefrom a latter sender is received (1005) at a message-handling IM client115 deployed by the recipient. Upon receiving (1005) the latter IMmessage, the message-handling IM client 115 determines (1010) whether ornot the recipient is engaged in an IM chat session with an earliersender. If it is determined (1010) that the recipient is not alreadyengaged in an IM chat session, then the process ends.

Conversely, if it is determined (1010) that the recipient is alreadyengaged in an IM chat session with an earlier sender, then themessage-handling IM client 115 queries (1015) the recipient for approvalto include the latter sender in the IM chat session already in progress.In some embodiments, the query may be a pop-up window that is displayedat the recipient's IM client. In other embodiments, the query may be anIM message text line that appears in the message window at therecipient's message-handling IM client 115. In the query, themessage-handling IM client 115 asks the recipient whether or not thelatter sender may participate in the IM chat session between therecipient and the earlier sender, which is already in progress. When therecipient replies to the query, the message-handling IM client 115receives (1020) the reply and determines (1025) whether or not therecipient has rejected the joining of the latter sender in the IM chatsession already in progress. If the message-handling IM client 115determines (1025) that the recipient has rejected the latter sender'sparticipation, then the process ends. If, however, the recipient hasapproved the latter sender's participation, then the message-handling IMclient 115 queries (1030) the latter sender by issuing an invitation tojoin the IM chat session already in progress. When the latter senderreplies to the query, the message-handling IM client 115 receives (1035)the reply and determines (1040) whether or not the latter sender hasaccepted the invitation. If the latter sender has rejected theinvitation to join the IM chat session already in progress, then theprocess ends. If, however, the latter sender has accepted theinvitation, then a three-way IM chat session is established (1045)between the earlier sender, the latter sender, and the recipient.

Using the example of Romeo and Juliet, the process of FIG. 10B mayprogress as follows. Initially, an IM chat session is establishedbetween Romeo (earlier sender) and Juliet (recipient). During this IMchat session, Mercutio (latter sender) sends an IM message to Juliet. Inresponse to Mercutio's IM message, Juliet's message-handling IM client115 determines that Juliet is engaged in an IM chat session with Romeo.Thus, Juliet's message-handling IM client 115 queries Juliet todetermine whether or not to invite Mercutio to join the IM chat sessionalready in progress between Juliet and Romeo. When Juliet indicates thatan invitation should be issued to Mercutio, the message-handling IMclient 115 issues an appropriate request to Mercutio and awaits a replyfrom Mercutio. When Mercutio accepts the invitation, a three-way IM chatsession is established between Romeo, Juliet, and Mercutio.

In some embodiments, the processes of FIGS. 8 through 10B may beperformed by the message-handling IM client 115 as shown in FIGS. 1through 3B. As shown in FIGS. 1 through 10B, the disclosed embodimentsprovide added functionality in handling IM messages, thereby providingfor a more versatile IM environment.

Having described systems and methods for increasing functionality in IMcommunications, attention is turned to FIGS. 11A and 11B, which providea user interface that implements additional IM functionality.

FIG. 11A is a diagram showing an embodiment of a user interface for anIM chat session. Specifically, FIG. 11A shows an IM chat session betweena customer and a customer support staff member (hereinafter “supportstaff”). As shown in FIG. 11A, during text IM, the support staff types atext message in an input area 1110 to a customer. Thereafter, thecustomer may reply to the support staffs text message. Thisback-and-forth exchange of text messages is often displayed in adialogue box 1105 at an IM chat window 1100 a, with themost-recently-displayed message 1120 typically being displayed at thebottom of the IM messages 1115. Hence, both the support staff and thecustomer may follow the history of the conversation by viewing the IMmessages 1115 displayed in the dialogue box 1105. As is known, the IMchat window 1100 a may include a scroll bar 1160 that permits thesupport staff to scroll portions of the IM messages 1115 that may havemoved beyond the visible area of the dialogue box 1105, as the supportstaff and the customer exchange IM messages 1115.

As is known to those of skill in the art, the IM chat window 1100 a mayalso include various function bars 1130, 1125 that include icons, suchas, color selection icons 1135 that permit the support staff to changethe foreground and background color of the dialogue box 1105, font sizemanipulation icons 1140 that permit the support staff to change the fontsize of the text, font type manipulation icons 1145 that permit thesupport staff to change the font size, a uniform resource locator (URL)icon 1150 that permits the support staff to send URL information, anemoticon icon 1155 that permits the support staff to display a varietyof emoticons (e.g., smiley faces, sad faces, etc.), a speaker icon 1165that permits the support staff to turn on or off incoming audio streams,an add-customer icon 1170 that permits the support staff to add thecustomer to the support staffs IM customer list, a block icon 1175 thatpermits the support staff to block or ignore the IM customer, an IMhistory icon 1180 that permits the support staff to begin or end loggingthe IM chat session, a customer information icon 1185 that permits thesupport staff to obtain additional information about the customer, andother icons that perform a variety of other IM functions.

Specifically, FIG. 11A shows an embodiment having an icon 1190 thatindicates to the support staff that a technical support member(hereinafter “technician”) is attempting to send an IM to the supportstaff while the support staff is engaged in an IM chat session with acustomer. For example, an embodiment of the process begins with acustomer and a support staff engaged in an IM chat session. As thecustomer and the support staff are exchanging IM chat messages 1115within the IM dialogue box 1105, a technician types an IM message to thesupport staff. As the technician is typing the IM message to the supportstaff, an icon 1190 appears in the IM chat window of the support staff.The icon 1190 indicates to the support staff that the technician iscurrently typing an IM chat message to the support staff. Alternatively,the icon 1190 indicates that the technician has sent an IM message tothe support staff. In some embodiments, the icon 1190 also acts as analert that prompts the support staff to determine whether or not thesupport staff wishes to include the technician as a participant in theIM chat session between the customer and the support staff. In someembodiments, when the support staff selects the icon 1190, themessage-handling IM client 1100 reconfigures the IM chat session from atwo-way IM chat session between the customer and the support staff to athree-way IM chat session between the customer, the support staff, andthe technician. In other words, when the technician attempts to send anIM to the support staff, and the support staff indicates that thetechnician should be a participant in the currently-established IM chatsession, the message-handling IM client 1100 converts the two-way IMchat session to a three-way IM chat session.

In some embodiments, if the support staff ignores the alert, then thetechnician is not included in the two-way IM chat session between thecustomer and the support staff. Alternatively, the IM client may providea mechanism by which the support staff may explicitly reject theincoming IM message from the technician. Also, in some embodiments, theIM client may provide a mechanism by which the support staff mayidentify that the IM chat session with the technician should be aseparate IM chat session than the IM chat session with the customer.

In other embodiments, such as that shown in FIG. 11B, the IM chat window1100 may include another icon 1195 (also referred to herein as“pre-invite icon” 1195) that configures the message-handling IM client1100 to poll for the presence of the technician. That pre-invite icon1195 may be customized by the support staff to initiate polling for thepresence of any individual that the support staff wishes to include inthe IM chat session. For those embodiments, where the message-handlingIM client 1100 has pre-invited the technician, when the status of thetechnician becomes present online, the message-handling IM client 1100of the support staff issues an invitation to the pre-invited technicianto join the IM chat session already in progress. Since mechanisms forinviting others to join IM chat sessions is known in the art, furtherdiscussion of invitations to join IM chat sessions is omitted here.

The pre-invite feature is particularly useful in business environmentswhere a support staff is attempting to answer a customer's questions,but needs the additional assistance of a technician to properly answerthe questions. For example, if a customer is engaged in an IM chatsession with a support staff because of technical problems experiencedby the customer for a particular computer-related product, then thepre-invite of a technician will allow the support staff to solicitparticipation of a technician in the solving of the technical problemwhen the technician becomes available. In this regard, when a technicianbecomes available (or present), an invitation is issued to thetechnician to join the IM chat session already in progress. Thus, ratherthan having the customer's questions relayed to the technician by thesupport staff through another IM chat session, the technician maydirectly engage the customer and the support staff to solve thetechnical problem.

In some embodiments, when the three-way IM chat session is established,the entire transcript of the IM chat session will be available to thetechnician so that the technician may be apprised of the dialoguebetween the customer and the support staff prior to the technician'sjoining the IM chat session.

As shown in FIGS. 11A and 11B, greater functionality in IMcommunications is achieved by providing capabilities to merge IM chatsessions.

The message-handling IM client 115 a . . . 115 c, the IM receive logic305, 307, the display logic 310, 312, the timing logic 315, theprompting logic 320, the presence logic 325, the convey logic 330, themessage-reply logic 340, the message-transfer logic 345, themessage-forward logic 350, the IM address append logic 355, theindicator messages 360, the IM addresses 335, session-tracker logic 317,sender-query logic 322, recipient-query logic 332, merge-determinationlogic 327, IM chat-session-merge logic 337, chat-room logic 342, andother logic components for carrying out the recited functions in thepresent invention can be implemented in hardware, software, firmware, ora combination thereof. In the preferred embodiment(s), themessage-handling IM client 115 a . . . 115 c, the IM receive logic 305,307, the display logic 310, 312, the timing logic 315, the promptinglogic 320, the presence logic 325, the convey logic 330, themessage-reply logic 340, the message-transfer logic 345, themessage-forward logic 350, the IM address append logic 355, theindicator messages 360, the IM addresses 335, session-tracker logic 317,sender-query logic 322, recipient-query logic 332, merge-determinationlogic 327, IM chat-session-merge logic 337, chat-room logic 342, andother logic components for carrying out the recited functions areimplemented in software or firmware that is stored in a memory and thatis executed by a suitable instruction execution system. If implementedin hardware, as in an alternative embodiment, the message-handling IMclient 115 a . . . 115 c, the IM receive logic 305, 307, the displaylogic 310, 312, the timing logic 315, the prompting logic 320, thepresence logic 325, the convey logic 330, the message-reply logic 340,the message-transfer logic 345, the message-forward logic 350, the IMaddress append logic 355, the indicator messages 360, the IM addresses335, session-tracker logic 317, sender-query logic 322, recipient-querylogic 332, merge-determination logic 327, IM chat-session-merge logic337, chat-room logic 342, and other logic components for carrying outthe recited functions can be implemented with any or a combination ofthe following technologies, which are all well known in the art: adiscrete logic circuit(s) having logic gates for implementing logicfunctions upon data signals, an application specific integrated circuit(ASIC) having appropriate combinational logic gates, a programmable gatearray(s) (PGA), a field programmable gate array (FPGA), etc.

Any process descriptions or blocks in flow charts should be understoodas representing modules, segments, or portions of code which include oneor more executable instructions for implementing specific logicalfunctions or steps in the process, and alternate implementations areincluded within the scope of the preferred embodiment of the presentinvention in which functions may be executed out of order from thatshown or discussed, including substantially concurrently or in reverseorder, depending on the functionality involved, as would be understoodby those reasonably skilled in the art of the present invention.

The message-handling IM client 115 a . . . 115 c may be implemented as acomputer program, which comprises an ordered listing of executableinstructions for implementing logical functions. As such, the messagehandling IM client 115 a . . . 115 c may be embodied in anycomputer-readable medium for use by or in connection with an instructionexecution system, apparatus, or device, such as a computer-based system,processor-containing system, or other system that can fetch theinstructions from the instruction execution system, apparatus, or deviceand execute the instructions. In the context of this document, a“computer-readable medium” can be any means that can contain, store,communicate, propagate, or transport the program for use by or inconnection with the instruction execution system, apparatus, or device.The computer-readable medium can be, for example but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, orsemiconductor system, apparatus, device, or propagation medium. Morespecific examples (a nonexhaustive list) of the computer-readable mediumwould include the following: an electrical connection (electronic)having one or more wires, a portable computer diskette (magnetic), arandom access memory (RAM) (electronic), a read-only memory (ROM)(electronic), an erasable programmable read-only memory (EPROM or Flashmemory) (electronic), an optical fiber (optical), and a portable compactdisc read-only memory (CDROM) (optical). Note that the computer-readablemedium could even be paper or another suitable medium upon which theprogram is printed, as the program can be electronically captured, viafor instance optical scanning of the paper or other medium, thencompiled, interpreted or otherwise processed in a suitable manner ifnecessary, and then stored

Although exemplary embodiments have been shown and described, it will beclear to those of ordinary skill in the art that a number of changes,modifications, or alterations may be made, none of which depart from thespirit of the present invention. For example, while the disclosedembodiments show the system as being implemented in a single IM-capabledevice such as, for example, a workstation, a PDA, or a cellulartelephone, it should be appreciated that the system may be implementedat the server-side, in which the auto-reply, auto-forward, and/orauto-message-transfer functions are performed by a server rather than bya client. Also, it should be appreciated that the above-describedfunctions may be implemented in a distributed network, where a serverand a client, in combination, perform the above-recited functions.Moreover, while the embodiments are described in the context of XML, itshould be appreciated that other IM protocols may be used to implementthe auto-reply, auto-forward, and/or auto-message-transfer functions.While automatic handling of IM messages have been described, it shouldbe appreciated that the auto-handling may be initiated by the recipient,rather than being initiated by an elapsed time. Hence, while fullyautomated message handling approaches are described herein, it should beappreciated that other embodiments may include manual intervention as apart of a semi-automated process. Also, while embodiments are shown inwhich IM chat sessions between a recipient and an earlier sender ismerged with an IM chat session between the recipient and a lattersender, it should be appreciated that, for some embodiments, multiple IMchat sessions that are already established may be merged. In thisregard, rather than waiting for an incoming IM message, a recipient maymerge IM chat sessions that are already in progress between multiplesenders. All such changes, modifications, and alterations shouldtherefore be seen as within the scope of the present invention.

1. A method for providing instant messaging chat sessions, the methodcomprising: receiving an instant messaging message from a sender to afirst recipient; displaying the instant messaging message to the firstrecipient; waiting for a response from the first recipient for a firstpredetermined time interval; determining if the response from the firstrecipient was sent to the sender during the first predetermined timeinterval by utilizing a processor; determining if the first recipient isalready engaged in a first instant messaging chat session with a contactif the response from the first recipient is determined not to be sent tothe sender during the first predetermined time interval; providing afirst message to the sender that notifies the sender to wait for asecond predetermined time interval for the response from the firstrecipient if the first recipient is determined to be already engaged inthe first instant messaging chat session with the contact; andestablishing a second instant messaging chat session between the senderand the first recipient if the first recipient sends the response duringthe second predetermined time interval.
 2. The method of claim 1,further comprising establishing a third instant messaging chat sessionbetween the sender and the first recipient if the first recipient sendsthe response during the first predetermined time interval.
 3. The methodof claim 1, further comprising transmitting a second message to thesender indicating that the first recipient is unavailable to engage in athird instant messaging chat session between the sender and the firstrecipient if the response from the first recipient is determined not tobe sent to the sender during the first predetermined time interval andif the first recipient is determined to not be already engaged in thefirst instant messaging chat session with the contact.
 4. The method ofclaim 1, further comprising transmitting a second message to the senderindicating the that first recipient is already engaged in the firstinstant messaging chat session with the contact if it is determined thatthe first recipient is engaged in the first instant messaging chatsession with the contact.
 5. The method of claim 1, further comprisingprompting the sender for permission to transmit the instant messagingmessage to a second recipient if the response from the first recipientis determined not to be sent to the sender during the firstpredetermined time interval.
 6. The method of claim 5, furthercomprising transmitting the instant messaging message to the secondrecipient if the sender provides permission to transmit the instantmessaging message to the second recipient.
 7. The method of claim 6,further comprising transmitting a notification to the second recipientthat the instant messaging message originated from the sender.
 8. Themethod of claim 5, further comprising establishing a third instantmessaging chat session between the sender and the second recipient ifthe sender provides permission to transmit the instant messaging messageto the second recipient.
 9. The method of claim 1, further comprisingquerying the first recipient for approval to add a second recipient tothe second instant messaging chat session between the sender and thefirst recipient.
 10. The method of claim 9, further comprising addingthe second recipient to the second instant messaging chat sessionbetween the sender and the first recipient if the first recipientprovides the approval.
 11. The method of claim 9, further comprisingrevealing instant messaging communications between the first recipientand the sender to the second recipient prior to adding the secondrecipient to the second instant messaging chat session.
 12. The methodof claim 1, further comprising transmitting the instant messagingmessage from the sender to the first recipient to a first instantmessaging address of the first recipient.
 13. The method of claim 12,further comprising transmitting the instant messaging message to asecond instant messaging address of the first recipient if the secondinstant messaging address was used more recently by the first recipientthan the first instant messaging address.
 14. A system for providinginstant messaging chat sessions, the system comprising: an electronicprocessor configured to: receive an instant messaging message from asender to a first recipient; display the instant messaging message tothe first recipient; wait for a response from the first recipient for afirst predetermined time interval; determine if the response from thefirst recipient was sent to the sender during the first predeterminedtime interval by utilizing a processor; determine if the first recipientis already engaged in a first instant messaging chat session with acontact if the response from the first recipient is determined not to besent to the sender during the first predetermined time interval; andprovide a first message to the sender that notifies the sender to waitfor a second predetermined time interval for the response from the firstrecipient if the first recipient is determined to be already engaged inthe first instant messaging chat session with the contact.
 15. Thesystem of claim 14, wherein the electronic processor is configured toestablish a second instant messaging chat session between the sender andthe first recipient if the first recipient sends the response during thesecond predetermined time interval.
 16. The system of claim 14, whereinthe electronic processor is configured to establish a third instantmessaging chat session between the sender and the first recipient if thefirst recipient sends the response during the first predetermined timeinterval.
 17. The system of claim 14, wherein the electronic processoris configured to prompt the sender for permission to transmit theinstant messaging message to a second recipient if the response from thefirst recipient is determined not to be sent to the sender during thefirst predetermined time interval.
 18. The system of claim 14, whereinthe electronic processor is configured to transmit the instant messagingmessage to the second recipient if the sender provides permission totransmit the instant messaging message to the second recipient.
 19. Thesystem of claim 17, wherein the electronic processor is configured toestablish a third instant messaging chat session between the sender andthe second recipient if the sender provides permission to transmit theinstant messaging message to the second recipient.
 20. A non-transitorycomputer-readable storage medium comprising instructions for causing anelectronic processor to: receive an instant messaging message from asender to a first recipient; wait for a response from the firstrecipient for a first predetermined time interval; determine if theresponse from the first recipient was sent to the sender during thefirst predetermined time interval by utilizing a processor; determine ifthe first recipient is already engaged in a first instant messaging chatsession with a contact if the response from the first recipient isdetermined not to be sent to the sender during the first predeterminedtime interval; and provide a first message to the sender that notifiesthe sender to wait for a second predetermined time interval for theresponse from the first recipient if the first recipient is determinedto be already engaged in the first instant messaging chat session withthe contact.